home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
bbsutil
/
bdoc_256.zip
/
BINK_250.DOC
< prev
next >
Wrap
Text File
|
1991-09-16
|
30KB
|
840 lines
Addendum to BinkleyTerm Documentation
Changes and Additions
for BinkleyTerm Version 2.50
Copyright (C) 1991 Bit Bucket Software, Co.
INTRODUCTION
Once again, the documentation for this latest release of BinkleyTerm is
being issued as an addendum to the previous docs. Information contained
herein should be considered as superseding any previous documentation.
We expect to have a comprehensive update for the BinkleyTerm docs by Q4
1991 or Q1-1992.
------------------------------------------------------------------------
--== WARNING!!! ==--
--== THIS VERSION IS NOT A PLUG IN UPGRADE FOR VERSION 2.40!!! ==--
------------------------------------------------------------------------
Bink 2.50 will MOST DEFINITELY break your 2.40 batch files, if you're
using the "BBS Spawn", "BBS Batch", or "ExtrnMail" methods of calling up
your BBS.
The way that Bink hands the baton to the BBS has changed - TWO bps
rates are now passed to the outside world. Previously, Bink would exit
with the following parameters written to the batch file:
For the "BBS Batch" and "BBS Spawn" methods,
OLD STYLE (v2.40 & earlier):
SPAWNBBS %1 %2 %3 %4
%1 = caller's connect rate as reported by the modem
%2 = the comm port in use
%3 = time to the next event in minutes
%4 = extended information in the modem connect string (/ARQ, etc)
For the "ExtrnMail" method,
OLD STYLE (v2.40 & earlier):
EXTMAIL %1 %2 %3 %4 %5
%1 = caller's connect rate as reported by the modem
%2 = the comm port in use
%3 = time to the next event in minutes
%4 = errorlevel exit from the original batch file
%5 = extended information in the modem connect string (/ARQ, etc)
NOW, BinkleyTerm 2.50 passes the link rate first, and the caller's
actual connect rate as the second parameter.
For the "BBS Batch" and "BBS Spawn" methods,
NEW STYLE (v2.50):
SPAWNBBS %1 %2 %3 %4 %5
%1 = speed of the computer-to-modem link rate in bps
%2 = caller's connect rate reported by the modem
%3 = the comm port in use
%4 = time to the next event in minutes
%5 = extended information in the modem connect string (/ARQ, etc)
For the "ExtrnMail" method,
NEW STYLE (v2.50):
EXTMAIL %1 %2 %3 %4 %5 %6
%1 = speed of the computer-to-modem link rate in bps
%2 = caller's connect rate reported by the modem
%3 = the comm port in use
%4 = time to the next event in minutes
%5 = errorlevel exit from the original batch file
%6 = extended information in the modem connect string (/ARQ, etc)
NOTE: If you're locking your FOSSIL driver, the link rate and connect
rate passed by BinkleyTerm will be the same (unless the connect
rate is one of the new HST-reported non-standard rates). Bink
has no way of knowing the port's been locked unless it does
the locking itself via the "Lockbaud" config verb. Please refer
to the detailed link/connect rate table later in this document
for further details.
For instance, if you previously used this line in your BBS batch file:
Opus Bbs -b%1 -p%2 -t%3
Change it to:
Opus Bbs -b%2 -p%3 -t%4
Of course, if you're using the "BBS Exit" method of calling up your BBS,
none of this affects you. What does affect you is Bink's ability to
recognize the new HST connect strings and how they're handled, explained
later.
--- o ---
Why the change to the batch files? There's a high-tech feature offered
by USRobotics' Courier HST, HST Dual Standard and Telebit's T2500 modems
that, used in combination with Bink's "LockBaud" config verb, will give
your callers with high-speed error-correcting modems the speed benefits
of a locked port and others will have the responsiveness of a normal
connection. If you are using one of these modems, the new "LockBaud"
options will allow you to make use of this feature.
NOTE: You can continue to use your current floating or locked port setup
by leaving the "LockBaud" config verb commented out and ignoring
the following.
If your HST or HST/DS is the older version with round LEDs, use your
favorite comm program (or Bink's terminal mode), type in "AT&$<RETURN>",
and see if "&B2" is listed as an option. If it is, you can use
"LockBaud /ARQ". All v.42bis-capable and newer rectangular LED HST &
HST/DS models support the "&B2" command.
If &B2's not listed, try typing in "ATS$<RETURN>", and see if S-Register 27's
bitmap options allow the port to be locked at 19200 and/or 38400 bps. If so,
use the &B0S27=nnn setup listed below, and you'll be able to lock, but only
at connect speeds of 4800 bps or greater, using "LockBaud 4800".
Courier HST and HST Dual Standards manufactured prior to February 1989
(those not supporting the S-register 27 lock options) will not be able to
utilize the new "LockBaud" options.
Here's how to install this new floating/locked setup:
1) DON'T lock your FOSSIL driver.
2) Enable "LockBaud /ARQ" in Binkley.Cfg (newer HST)
"Lockbaud 4800" in Binkley.Cfg (older HST)
-or-
"LockBaud /REL" in Binkley.Cfg (T2500)
3) Store "&A1", "&A2" or "&A3" in non-volatile RAM to
enable the /ARQ extended result strings (HST)
4) Store "&B2" in non-volatile RAM (newer HST)
Store "&B0S27=128" for 19200 locking (older HST)
Store "&B0S27=192" for 38400 locking (older HST)
-or-
Store "S66=2" in non-volatile RAM (T2500)
5) If your BBS software allows you to pass the port rate separately
(as with Maximus v1.02), call up the BBS as follows:
Max Bbs -b%2 -p%3 -t%4 -s%1
(where %1 is the port rate and %2 is the connect rate)
6) If your BBS doesn't allow passing the link (port) speed
separately from the connect speed (as with Opus), you can use
the following kludge in your SPAWNBBS or EXTMAIL batch file
(using X00's XU.EXE or the similar utility included with your
FOSSIL driver):
Rem convert 1-based port from Bink to 0-based for XU
If "%3" == "1" SET PORT=0
If "%3" == "2" SET PORT=1
.
.
Rem it's always OK to lock with XU since unlock follows
XU LOCK:%PORT%:%1
Opus Bbs -b%2 -p%3 -t%4
if ERRORLEVEL . .
.
.
Rem unlock the port
XU LOCK:%PORT%:OFF
Note that Opus uses a 1-based comm port number, but XU & X00
use a 0-based comm port number.
In the docs for Opus 1.72a, this alternative method has been described:
NOTE: This behavior has NOT been verified!
------------------------------------------------------------------------
New command-line parameter: -a[modem string]
This ONLY affects people who are using Binkley 2.5+ and HST/DS
modems and the Dual Standard's &B2 option!
Binkley 2.50 will be sending the modem connect string infor-
mation, the stuff after the baud rate, out as a separate para-
meter. I don't remember exactly the sequence, but for Opus 1.72
there are two ways to handle it:
(Example! I don't know exactly how Binkley is handling this!)
%1 User Baud
%2 Port
%3 Time to next event
%4 Locked Baud
%5 Extended modem information.
From a batch file you would call Opus as:
Opus bbs -b%1 -p%2 -t%3 -a%5
However, Opus will ALSO accept this:
Opus bbs -b%1%5 -p%2 -t%3
Either way Opus will see the /ARQ and know that if &B2 has been
configured that the baud rate is locked, if the /ARQ is not
there, the baud rate will float.
---------------------